| V-56277 | High | Oracle WebLogic must uniquely identify and authenticate users (or processes acting on behalf of users). | To assure accountability and prevent unauthorized access, application server users must be uniquely identified and authenticated.
The application server must uniquely identify and authenticate... |
| V-56291 | High | Oracle WebLogic must encrypt passwords during transmission. | Passwords need to be protected at all times, and encryption is the standard method for protecting passwords during transmission.
Application servers have the capability to utilize either... |
| V-56293 | High | Oracle WebLogic must utilize encryption when using LDAP for authentication. | Passwords need to be protected at all times, and encryption is the standard method for protecting passwords during transmission.
Application servers have the capability to utilize LDAP... |
| V-56279 | High | Oracle WebLogic must authenticate users individually prior to using a group authenticator. | To assure individual accountability and prevent unauthorized access, application server users (and any processes acting on behalf of application server users) must be individually identified and... |
| V-56223 | Medium | Oracle WebLogic must enforce the organization-defined time period during which the limit of consecutive invalid access attempts by a user is counted. | By limiting the number of failed login attempts, the risk of unauthorized system access via automated user password guessing, otherwise known as brute-forcing, is reduced. Best practice requires a... |
| V-56315 | Medium | Oracle WebLogic must protect the integrity and availability of publicly available information and applications. | The purpose of this control is to ensure organizations explicitly address the protection needs for public information and applications, with such protection likely being implemented as part of... |
| V-56377 | Medium | Oracle WebLogic must only generate error messages that provide information necessary for corrective actions without revealing sensitive or potentially harmful information in error logs and administrative messages. | Any application providing too much information in error logs and in administrative messages to the screen risks compromising the data and security of the application and system. The structure and... |
| V-56379 | Medium | Oracle WebLogic must restrict error messages so only authorized personnel may view them. | If the application provides too much information in error logs and administrative messages to the screen, this could lead to compromise. The structure and content of error messages need to be... |
| V-56271 | Medium | Oracle WebLogic must adhere to the principles of least functionality by providing only essential capabilities. | Application servers provide a myriad of differing processes, features and functionalities. Some of these processes may be deemed to be unnecessary or too insecure to run on a production DoD... |
| V-56249 | Medium | Oracle WebLogic must provide the ability to write specified audit record content to an audit log server. | Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes, but is not... |
| V-56219 | Medium | Oracle WebLogic must provide access logging that ensures users who are granted a privileged role (or roles) have their privileged activity logged. | In order to be able to provide a forensic history of activity, the application server must ensure users who are granted a privileged role or those who utilize a separate distinct account when... |
| V-56337 | Medium | Oracle WebLogic must protect against or limit the effects of HTTP types of Denial of Service (DoS) attacks. | Employing increased capacity and bandwidth combined with service redundancy can reduce the susceptibility to some DoS attacks. When utilizing an application server in a high risk environment (such... |
| V-56215 | Medium | Oracle WebLogic must automatically audit account creation. | Application servers require user accounts for server management purposes, and if the creation of new accounts is not logged, there is limited or no capability to track or alarm on account... |
| V-56313 | Medium | Oracle WebLogic must utilize NSA-approved cryptography when protecting classified compartmentalized data. | Cryptography is only as strong as the encryption modules/algorithms employed to encrypt the data.
Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to... |
| V-56217 | Medium | Oracle WebLogic must automatically audit account modification. | Once an attacker establishes initial access to a system, they often attempt to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to simply modify... |
| V-56211 | Medium | Oracle WebLogic must ensure remote sessions for accessing security functions and security-relevant information are audited. | Auditing must be utilized in order to track system activity, assist in diagnosing system issues and provide evidence needed for forensic investigations post security incident.
Remote access by... |
| V-56317 | Medium | Oracle WebLogic must separate hosted application functionality from Oracle WebLogic management functionality. | Application server management functionality includes functions necessary to administer the application server and requires privileged access via one of the accounts assigned to a management role.... |
| V-56213 | Medium | Oracle WebLogic must support the capability to disable network protocols deemed by the organization to be nonsecure except for explicitly identified components in support of specific operational requirements. | Some networking protocols may not meet organizational security requirements to protect data and components.
Application servers natively host a number of various features such as management... |
| V-56295 | Medium | Oracle WebLogic, when utilizing PKI-based authentication, must validate certificates by constructing a certification path with status information to an accepted trust anchor. | A trust anchor is an authoritative entity represented via a public key and associated data. It is used in the context of public key infrastructures, X.509 digital certificates, and DNSSEC.
When... |
| V-56297 | Medium | Oracle WebLogic must map the PKI-based authentication identity to the user account. | The cornerstone of the PKI is the private key used to encrypt or digitally sign information. The key by itself is a cryptographic value that does not contain specific user information.... |
| V-56299 | Medium | Oracle WebLogic must use cryptographic modules that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance when encrypting stored data. | Encryption is only as good as the encryption modules utilized. Unapproved cryptographic module algorithms cannot be verified and cannot be relied upon to provide confidentiality or integrity, and... |
| V-56269 | Medium | Oracle WebLogic must limit privileges to change the software resident within software libraries (including privileged programs). | Application servers have the ability to specify that the hosted applications utilize shared libraries. The application server must have a capability to divide roles based upon duties wherein one... |
| V-56305 | Medium | Oracle WebLogic must employ strong identification and authentication techniques when establishing nonlocal maintenance and diagnostic sessions. | Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal... |
| V-56247 | Medium | Oracle WebLogic must produce audit records containing sufficient information to establish the identity of any user/subject or process associated with the event. | Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control, includes: time stamps,... |
| V-56303 | Medium | Oracle WebLogic must employ cryptographic encryption to protect the integrity and confidentiality of nonlocal maintenance and diagnostic communications. | Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the Internet) or an internal... |
| V-56301 | Medium | Oracle WebLogic must utilize FIPS 140-2 approved encryption modules when authenticating users and processes. | Encryption is only as good as the encryption modules utilized. Unapproved cryptographic module algorithms cannot be verified and cannot be relied upon to provide confidentiality or integrity, and... |
| V-56265 | Medium | Oracle WebLogic must protect audit tools from unauthorized modification. | Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data.
Depending upon the log format and application, system and application log tools may... |
| V-56343 | Medium | Oracle WebLogic must fail securely in the event of an operational failure. | Fail secure is a condition achieved by the application server in order to ensure that in the event of an operational failure, the system does not enter into an unsecure state where intended... |
| V-56267 | Medium | Oracle WebLogic must protect audit tools from unauthorized deletion. | Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data.
Depending upon the log format and application, system and application log tools may... |
| V-56341 | Medium | Oracle WebLogic must limit the use of resources by priority and not impede the host from servicing processes designated as a higher-priority. | Priority protection helps the application server prevent a lower-priority application process from delaying or interfering with any higher-priority application processes. If the application server... |
| V-56347 | Medium | Oracle WebLogic must employ approved cryptographic mechanisms when transmitting sensitive data. | Preventing the disclosure of transmitted information requires that application servers take measures to employ approved cryptography in order to protect the information during transmission over... |
| V-56263 | Medium | Oracle WebLogic must protect audit tools from unauthorized access. | Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data.
Depending upon the log format and application, system and application log tools may... |
| V-56309 | Medium | Oracle WebLogic must establish a trusted communications path between the user and organization-defined security functions within the information system. | Without a trusted communication path, the application server is vulnerable to a man-in-the-middle attack.
Application server user interfaces are used for management of the application server so... |
| V-56329 | Medium | Oracle WebLogic must protect the confidentiality of applications and leverage transmission protection mechanisms, such as TLS and SSL VPN, when deploying applications. | Preventing the disclosure of transmitted information requires that applications take measures to employ some form of cryptographic mechanism in order to protect the information during... |
| V-56209 | Medium | Oracle WebLogic must employ automated mechanisms to facilitate the monitoring and control of remote access methods. | Remote network access is accomplished by leveraging common communication protocols and establishing a remote connection.
Application servers provide remote management access and need to provide... |
| V-56207 | Medium | Oracle WebLogic must use cryptography to protect the integrity of the remote access session. | Encryption is critical for protection of remote access sessions. If encryption is not being used for integrity, malicious users may gain the ability to modify the application server configuration.... |
| V-56205 | Medium | Oracle WebLogic must utilize cryptography to protect the confidentiality of remote access management sessions. | Remote management access is accomplished by leveraging common communication protocols and establishing a remote connection to the application server via a network for the purposes of managing the... |
| V-56327 | Medium | Oracle WebLogic must be configured to perform complete application deployments. | Failure to a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the information system or a component of the system.
When an... |
| V-56225 | Medium | Oracle WebLogic must automatically lock accounts when the maximum number of unsuccessful login attempts is exceeded for an organization-defined time period or until the account is unlocked by an administrator. | Anytime an authentication method is exposed so as to allow for the utilization of an application interface, there is a risk that attempts will be made to obtain unauthorized access.
By locking... |
| V-56321 | Medium | Oracle WebLogic must ensure authentication of both client and server during the entire session. | This control focuses on communications protection at the session, versus packet level.
At the application layer, session IDs are tokens generated by web applications to uniquely identify an... |
| V-56227 | Medium | Oracle WebLogic must protect against an individual falsely denying having performed a particular action. | Non-repudiation of actions taken is required in order to maintain application integrity. Examples of particular actions taken by individuals include creating information, sending a message,... |
| V-56323 | Medium | Oracle WebLogic must terminate user sessions upon user logout or any other organization- or policy-defined session termination events such as idle time limit exceeded. | If communications sessions remain open for extended periods of time even when unused, there is the potential for an adversary to hijack the session and use it to gain access to the device or... |
| V-56287 | Medium | Oracle WebLogic must enforce password complexity by the number of numeric characters used. | Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Use of a complex password helps to increase the time... |
| V-56221 | Medium | Oracle WebLogic must limit the number of failed login attempts to an organization-defined number of consecutive invalid attempts that occur within an organization-defined time period. | Anytime an authentication method is exposed so as to allow for the login to an application, there is a risk that attempts will be made to obtain unauthorized access.
By limiting the number of... |
| V-56285 | Medium | Oracle WebLogic must enforce password complexity by the number of lower-case characters used. | Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Use of a complex password helps to increase the time... |
| V-56283 | Medium | Oracle WebLogic must enforce password complexity by the number of upper-case characters used. | Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Use of a complex password helps to increase the time... |
| V-56281 | Medium | Oracle WebLogic must enforce minimum password length. | Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Password length is one of several factors that helps... |
| V-56273 | Medium | Oracle WebLogic must prohibit or restrict the use of unauthorized functions, ports, protocols, and/or services. | Application servers provide numerous processes, features, and functionalities that utilize TCP/IP ports. Some of these processes may be deemed to be unnecessary or too insecure to run on a... |
| V-56387 | Medium | Oracle WebLogic must be integrated with a tool to implement multi-factor user authentication. | Multifactor authentication is defined as: using two or more factors to achieve authentication.
Factors include:
(i) something a user knows (e.g., password/PIN);
(ii) something a user has... |
| V-56385 | Medium | Oracle WebLogic must be managed through a centralized enterprise tool. | The application server can host multiple applications which require different functions to operate successfully but many of the functions are capabilities that are needed for all the hosted... |
| V-56383 | Medium | Oracle WebLogic must be integrated with a tool to monitor audit subsystem failure notification information that is sent out (e.g., the recipients of the message and the nature of the failure). | It is critical that, when a system is at risk of failing to process audit logs, it detects and takes action to mitigate the failure. As part of the mitigation, the system must send a notification... |
| V-56289 | Medium | Oracle WebLogic must enforce password complexity by the number of special characters used. | Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks.
Use of a complex password helps to increase the time... |
| V-56381 | Medium | Oracle WebLogic must provide system notifications to a list of response personnel who are identified by name and/or role. | Incident response applications are, by their nature, designed to monitor, detect, and alarm on defined events occurring on the system or on the network. A large part of their functionality is the... |
| V-56257 | Low | Oracle WebLogic must use internal system clocks to generate time stamps for audit records. | Without the use of an approved and synchronized time source, configured on the systems, events cannot be accurately correlated and analyzed to determine what is transpiring within the application... |
| V-56237 | Low | Oracle WebLogic must produce process events and security levels to establish what type of Oracle WebLogic process events and severity levels occurred. | Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control, includes: time stamps,... |
| V-56235 | Low | Oracle WebLogic must produce audit records containing sufficient information to establish what type of JVM-related events and severity levels occurred. | Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control, includes: time stamps,... |
| V-56233 | Low | Oracle WebLogic must produce process events and severity levels to establish what type of HTTPD-related events and severity levels occurred. | Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes time stamps,... |
| V-56231 | Low | Oracle WebLogic must generate audit records for the DoD-selected list of auditable events. | Audit records can be generated from various components within the application server. The list of audited events is the set of events for which audits are to be generated.
This set of events is... |
| V-56259 | Low | Oracle WebLogic must synchronize with internal information system clocks which, in turn, are synchronized on an organization-defined frequency with an organization-defined authoritative time source. | Determining the correct time a particular application event occurred on a system is critical when conducting forensic analysis and investigating system events.
Synchronization of system clocks... |
| V-56351 | Low | Oracle WebLogic must identify potentially security-relevant error conditions. | The structure and content of error messages need to be carefully considered by the organization and development team. The extent to which the application server is able to identify and handle... |
| V-56239 | Low | Oracle WebLogic must produce audit records containing sufficient information to establish when (date and time) the events occurred. | Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes time stamps,... |
| V-56253 | Low | Oracle WebLogic must alert designated individual organizational officials in the event of an audit processing failure. | Audit processing failures include, but are not limited to, failures in the application server log capturing mechanisms or audit storage capacity being reached or exceeded. In some instances, it... |
| V-56333 | Low | Oracle WebLogic must protect the integrity of applications during the processes of data aggregation, packaging, and transformation in preparation for deployment. | Information can be subjected to unauthorized changes (e.g., malicious and/or unintentional modification) at information aggregation or protocol transformation points. It is therefore imperative... |
| V-56255 | Low | Oracle WebLogic must notify administrative personnel as a group in the event of audit processing failure. | Audit processing failures include software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded. To ensure flexibility and ease of... |
| V-56275 | Low | Oracle WebLogic must utilize automated mechanisms to prevent program execution on the information system. | The application server must provide a capability to halt or otherwise disable the automatic execution of deployed applications until such time that the application is considered part of the... |
| V-56243 | Low | Oracle WebLogic must produce audit records containing sufficient information to establish the sources of the events. | Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes, but is not... |
| V-56307 | Low | Oracle WebLogic must terminate the network connection associated with a communications session at the end of the session or after a DoD-defined time period of inactivity. | If communications sessions remain open for extended periods of time even when unused, there is the potential for an adversary to hijack the session and use it to gain access to the device or... |
| V-56241 | Low | Oracle WebLogic must produce audit records containing sufficient information to establish where the events occurred. | Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes time stamps,... |
| V-56245 | Low | Oracle WebLogic must produce audit records that contain sufficient information to establish the outcome (success or failure) of application server and application events. | Information system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes, but is not... |
| V-56261 | Low | Oracle WebLogic must protect audit information from any type of unauthorized read access. | If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is difficult, if not impossible, to achieve. In... |
| V-56229 | Low | Oracle WebLogic must compile audit records from multiple components within the system into a system-wide (logical or physical) audit trail that is time-correlated to within an organization-defined level of tolerance. | Audit generation and audit records can be generated from various components within the application server. The list of audited events is the set of events for which audits are to be generated.... |
| V-56251 | Low | Oracle WebLogic must provide a real-time alert when organization-defined audit failure events occur. | It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Audit processing failures include software/hardware errors, failures... |
